Xm-tests 01_memset_basic_pos.test and 03_memset_random_pos.test start
authoremellor@leeni.uk.xensource.com <emellor@leeni.uk.xensource.com>
Tue, 2 May 2006 17:17:59 +0000 (18:17 +0100)
committeremellor@leeni.uk.xensource.com <emellor@leeni.uk.xensource.com>
Tue, 2 May 2006 17:17:59 +0000 (18:17 +0100)
commite5fb08210d9c44e7f5addca77263080ebdcf5dd4
treea5df82b2904e2d54bdba92d2344c831811dd0925
parent9a10a080aa1f28c88312b9cf3b229b3dcd169e63
Xm-tests 01_memset_basic_pos.test and 03_memset_random_pos.test start
domUs with 64MB of memory,
and assume that all of that memory is available in the domU. They then
perform various xm memset tests
based on the assumed starting conditions.

When netback & blkback are comiled into the domU kernel, they eat about
5MB. This mismatch will cause
01_memset_basic_pos.test to fail every time. 03_memset_random_pos.test
will probably fail, but can
pass with some lucky numbers from the random number generator.

This patch changes both tests to read the starting memory allocation from
the balloon driver in the domU.

Signed-off-by: Jim Dykman <dykman@us.ibm.com>
tools/xm-test/tests/memset/01_memset_basic_pos.py
tools/xm-test/tests/memset/03_memset_random_pos.py